-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
[Quantization] Add compressed-tensors NVFP4 MoE Support #19990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @dsikka, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request significantly enhances vLLM's quantization capabilities by adding comprehensive support for NVFP4 quantization specifically for Mixture-of-Experts (MoE) models. It introduces a new quantization method that handles the unique structure of NVFP4 weights and integrates with optimized Marlin kernels to ensure high-performance inference for these quantized models.
Highlights
- NVFP4 MoE Support: Introduced
CompressedTensorsW4A4MoeMethod
to enable support for NVFP4 (NVIDIA FP4) quantized Mixture-of-Experts (MoE) models, allowing for more efficient inference with these models. - Marlin Kernel Integration: Leveraged highly optimized Marlin kernels for the efficient execution of NVFP4 MoE operations, ensuring performance benefits for quantized models.
- Quantized Weight Handling: Implemented the loading and processing of NVFP4 quantized weights, including packed 4-bit weights (
torch.uint8
), FP8 block scales (torch.float8_e4m3fn
), and FP32 global scales, which are crucial for the new quantization scheme. - Dynamic Method Selection: Updated the quantization method selection logic to correctly identify and instantiate the new NVFP4 MoE method based on the detected quantization configuration.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request adds support for MoE models with nvfp4 compressed tensors. The changes include modifications to the weight loader in fused_moe/layer.py
and the addition of a new class CompressedTensorsW4A4MoeMethod
in compressed_tensors_moe.py
to handle the new quantization method. There are several blocks of code that are commented out, and a breakpoint that should be removed.
vllm/model_executor/layers/quantization/compressed_tensors/compressed_tensors_moe.py
Outdated
Show resolved
Hide resolved
assert activation == "silu", "Only SiLU activation is supported." | ||
assert not apply_router_weight_on_input, ( | ||
"Router weight on input is not " | ||
"supported for ModelOptNvFp4FusedMoE.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These should still be enforced for fused_marlin_moe. Also update the mention of ModelOptNvFp4FusedMoE
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should they have been enforced in the ModelOpt integration?
return torch.ops.vllm.fused_marlin_moe( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, definitely there as well
vllm/model_executor/layers/quantization/compressed_tensors/compressed_tensors_moe.py
Outdated
Show resolved
Hide resolved
This pull request has merge conflicts that must be resolved before it can be |
Signed-off-by: Dipika Sikka <[email protected]>
Signed-off-by: Dipika Sikka <[email protected]>
Signed-off-by: Dipika <[email protected]>
… move utils Signed-off-by: Dipika <[email protected]>
Signed-off-by: Dipika <[email protected]>
Signed-off-by: Dipika Sikka <[email protected]>
@mgoin I would like to add a test but I am mindful of the test time for MoEs being added to the quantization tests - Maybe deepseek-ai/DeepSeek-V2-Lite? Do we have MoE tests beyond the weight loading tests. I guess lm-eval tests? I can add it in a follow-up |
Signed-off-by: Dipika Sikka <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! We can followup with the automated testing
Note:
cuda_archs_loose_intersection
to fix this PR which currently prevents buildingcutlass_moe_fp4
on b200Purpose
Test Plan
nm-testing/Qwen3-30B-A3B-NVFP4
e2e with tp>=1Generations: